Navigating using an indoor map representation

ABSTRACT

A method and system for providing an indoor map representation are provided herein. Aspects of this disclosure provide a representation of an indoor map environment whereby navigable areas are represented by a series of convex polygons in adjacency relationships with one another. Image analysis may be performed on a floor plan image to identify navigable areas and to determine the boundaries of the polygons, such as by assigning one or more colors to navigable space and one or more colors to non-navigable space. Route-finding operations may be performed using the adjacency relationships to find a path from a source area to a destination area.

The present application is a continuation of U.S. patent application Ser. No. 14/118,714, filed on Nov. 19, 2013, which application is a national phase entry under 35 U.S.C. §371 of International Application No. PCT/CN2012/070288, filed Jan. 12, 2012, all of which are incorporated herein by reference.

The proliferation of smart phones and other mobile devices has placed more processing power in the hands of consumers than ever before. These mobile devices are capable of executing a variety of applications, including applications that assist with navigation and route-finding. Traditional global positioning system (GPS) navigation devices are used to assist automobile owners with driving operations from a source to a destination, and navigation software is generally developed with the use-case of driving directions in mind. These devices may provide map data in the form of a road graph, with valid driving paths represented by line segments which intersect at various points, and which have a directionality element indicating valid directions of travel along the line segments. Such a design is efficient for use in situations where the user is travelling via a vehicle, as the vehicle is limited to particular pathways of travel.

However, as mobile devices increasingly contain route finding software, various solutions that provide for walking and indoor navigation have also been developed. The road graph as described above is not suitable for a walking or indoor environment because it may be overly complicated for a mobile device to process, and because users generally travel within open space, rather than along set pathways. When finding the path between two points on a map in a road graph model, if an end point is not located on the road, the end point may be approximated by a point on a road using a metric such as the shortest distance to the point. For this reason, such representations may not be optimal for areas with open space or other navigable space that cannot be efficiently represented by line segments. For example, an indoor map using a road graph representation might represent hallways and corridors as line segments. Such a representation may incorrectly identify a user as located within a hallway when in fact they are present in a room connected to that hallway. Thus, navigation map data provided by a road graph may be overly complicated and inefficient for the purposes of providing a representation of an indoor navigation environment.

BRIEF SUMMARY

A method and system for navigating using an indoor map representation are provided herein. Aspects of this disclosure provide a representation of an indoor map environment whereby navigable areas are represented by a series of convex polygons in adjacency relationships with one another. Route-finding operations may be performed using the adjacency relationships to find a path from a source area to a destination area.

Aspects of the disclosure describe a computer-implemented method for providing indoor navigation. The method may include determining a client location, identifying the client location as being within a source polygon selected from a plurality of convex polygons, determining a destination polygon associated with a destination location, determining, using a processor, a route from the source polygon to the destination polygon using the map model by identifying a path defined by the set of adjacency relationships, and providing the route from the source polygon to the destination polygon as a navigation path from the client location to the destination location. The plurality of convex polygons may be defined by a map model that comprises the plurality of convex polygons and a set of adjacency relationships among the plurality of convex polygons, where the plurality of convex polygons are associated with navigable space within a given geographical area. The set of adjacency relationships may be line segments representing the boundaries between polygons. The plurality of convex polygons may define the entirety of navigable space in an area. The navigable space may be contiguous. The map model may be generated using a building floor plan. The map model may further include metadata associated with one or more of the plurality of polygons. The method may further include determining the destination polygon by searching the metadata. The map model may include a series of vertices that define the plurality of polygons, where the series of vertices may be associated with location coordinates within the given geographical area.

Aspects of the disclosure may also provide a non-transitory computer readable medium comprising instructions that, when executed by a processor, cause the processor to perform a method. The method performed by the processor may include determining a client location, identifying the client location as being within a source polygon selected from a plurality of convex polygons, determining a destination polygon associated with a destination location, determining, using a processor, a route from the source polygon to the destination polygon using the map model by identifying a path defined by the set of adjacency relationships, and providing the route from the source polygon to the destination polygon as a navigation path from the client location to the destination location. The plurality of convex polygons may be defined by a map model that comprises the plurality of convex polygons and a set of adjacency relationships among the plurality of convex polygons. The plurality of convex polygons may be associated with navigable space within a given geographical area. The set of adjacency relationships may be line segments representing the boundaries between polygons. The plurality of convex polygons may define the entirety of navigable space in an area. The navigable space may be contiguous. The map model may be generated using a building floor plan. The map model may further include metadata associated with one or more of the plurality of polygons and wherein the method further comprises determining the destination polygon by searching the metadata. The map model may further include a series of vertices that define the plurality of polygons, wherein the series of vertices are associated with location coordinates within the given geographical area.

Aspects of the disclosure may provide a processing system for providing indoor navigation. The processing system may include a navigation element for providing a current location of the processing system, at least one processor, and a memory coupled to the at least one processor. The memory may store a map model that includes a plurality of convex polygons and a set of adjacency relationships among the plurality of convex polygons, where the plurality of convex polygons may be associated with navigable space within a given geographical area. The at least one processor may be configured to identify the current location provided by the navigation element as being within a source polygon selected from the plurality of convex polygons, determine a destination polygon associated with a destination location, determine a route from the source polygon to the destination polygon using the map model by identifying a path defined by the set of adjacency relationships, and provide the route from the source polygon to the destination polygon as a navigation path from the client location to the destination location. The set of adjacency relationships may be line segments representing the boundaries between polygons. The plurality of convex polygons may define the entirety of navigable space in an area. The navigable space may be contiguous. The map model may be generated using a building floor plan. The map model may further include metadata associated with one or more of the plurality of polygons. The processor may be further configured to determine the destination polygon by searching the metadata. The map model may include a series of vertices that define the plurality of polygons. The series of vertices may be associated with location coordinates within the given geographical area.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system diagram depicting an example of an indoor navigation system in accordance with aspects of the disclosure.

FIG. 2 is block diagram depicting an example of a map model generated from a floor plan in accordance with aspects of the disclosure.

FIG. 3 is a diagram depicting an example of a map model overlaid on a floor plan image in accordance with aspects of the disclosure.

FIG. 4 is a flow diagram depicting an example of a method for generating a map model from a floor plan image in accordance with aspects of the disclosure.

FIG. 5 is a flow diagram depicting an example of a method for navigating using an indoor map model in accordance with aspects of the disclosure.

DETAILED DESCRIPTION

A method and system for navigating using an indoor map representation are described here. Aspects of this disclosure provide an efficient representation of an indoor environment that can be used to perform navigation and route-finding operations. The indoor map representation may be provided to a client device as a series of vertices that describe a series of polygons and relationship data that identifies the adjacency relationships among the polygons. These polygons may identify areas of navigable space within the indoor environment. This indoor map representation may be used to perform route-finding operations from a source point to a destination point by identifying a path across adjacent polygons.

FIG. 1 is a system diagram depicting an example of an indoor navigation system 100 in accordance with aspects of the disclosure. As shown in FIG. 1, an example indoor navigation system 100 includes a server 102 and a client 104 in communication via a network 134. The server 102 may provide a map model 118 to the client 134 for use in navigation operations. The server 102 may generate the map model 118 using a floor plan image 116.

The server 102 may include a processor 106, a memory 108 and other components typically present in general purpose computers. The memory 108 may store instructions 110 and data 112 that are accessible by the processor 106. The processor 106 may execute the instructions 110 and access the data 112 to control the operations of the server 102.

The processor 106 may be any suitable processor, such as various commercially available general purpose processors. Alternatively, the processor 106 may be a dedicated controller such as an application-specific integrated circuit (“ASIC”) or a field-programmable gate array (“FPGA”).

The memory 108 may be any type of tangible memory operative to store information accessible by the processor 106, including a computer-readable medium, or other medium that stores data that may be read with the aid of an electronic device, such as a hard-drive, memory card, read-only memory (“ROM”), random access memory (“RAM”), digital versatile disc (“DVD”) or other optical disks, as well as other write-capable and read-only memories. The system and method may include different combinations of the foregoing, whereby different portions of the instructions and data are stored on different types of media.

Although FIG. 1 functionally illustrates the processor 106 and memory 108 as each being within a single block respectively, it should be understood that the processor 106 and memory 108 may actually comprise multiple processors and memories that may or may not be stored within the same physical housing. Accordingly, references to a processor, computer or memory will be understood to include references to a collection of processors, computers or memories that may or may not operate in parallel.

The instructions 112 may be any set of instructions to be executed directly (such as machine code) or indirectly (such as scripts) by the processor 108. For example, the instructions 112 may be stored as computer code on a non-transitory computer-readable medium. In that regard, the terms “instructions” and “programs” may be used interchangeably herein. The instructions 112 may be stored in object code format for direct processing by the processor 108, or in any other computer language including scripts or collections of independent source code modules that are interpreted on demand or compiled in advance. Functions, methods and routines of the instructions are explained in more detail below (see FIGS. 3-5).

In order to facilitate the map model generation operations of the server 102, the instructions 112 may comprise a model generator 114. The model generator 114 may create a map model 118 using a floor plan image 116. The floor plan image 116 may be any image relating to a building floor plan or an indoor or outdoor map. The map generator 114 may analyze the floor plan image 116 stored within the data 112 to identify navigable and non-navigable areas, and to generate one or more polygons to fill the navigable areas. These polygons may be used to create the map model 118, which may also be stored within the data 112. The map model 118 may be provided to the client 104 for use in navigation operations. The floor plan image 116 may be provided in any image format, such as bitmap, JPEG, GIF, TIFF, PDF, DXF, AUG, or any other image format that can be analyzed by a computer to identify navigable and non-navigable areas.

The data 112 may be retrieved, stored or modified by the processor 106 in accordance with the instructions 110. For instance, although the architecture is not limited by any particular data structure, the data may be stored in computer registers, in a relational database as a table having a plurality of different fields and records, Extensible Markup Language (“XML”) documents or flat files. The data may also be formatted in any computer readable format such as, but not limited to, binary values or Unicode. The data may comprise any information sufficient to identify the relevant information, such as numbers, descriptive text, proprietary codes, references to data stored in other areas of the same memory or different memories (including other network locations) or information that is used by a function to calculate the relevant data. Although a number of discrete modules and data sets (e.g., 114, 116, 118) are identified in connection with the server 102, the functionality of these modules and data may overlap and/or exist in a fewer or greater number of modules than what is shown, with such modules residing at one or more processing devices, which may be geographically dispersed.

The server 102 may be at one node of a network and be operative to directly and indirectly communicates with other nodes of the network. For example, the server 102 may comprise a web server that is operative to communicate with the client 104 via the network such that the server 102 transmits the map model 118 to the client 104 for use in navigation operations, or provides navigation routing information using the map model 118 using information provided by the client 104.

The client 104 may comprise a personal computer, a personal digital assistants (“PDA”), a tablet PC, a netbook, a rack mounted server, a laptop, a mobile phone, a smart phone etc. Indeed, the client 104 in accordance with the systems and methods described herein may comprise any device operative to process instructions and transmit data to and from humans and/or other computers including general purpose computers, network computers lacking local storage capability, etc.

The client 104 may be similarly configured to the server 102 as described above. For example, the client 104 may comprise a processor 120 coupled to a memory 122. As described above with respect to the memory 108, the memory 122 may include instructions 126 and data 128. The instructions 126 may include a navigation application 130.

The navigation application 130 operates to provide a user of the client 104 with navigation services, such as providing directions from the user's current location to a destination, or determination of the user's current location. The navigation application 130 may interface with a positioning element 124 to receive the current location of the client 104. For example the positioning element 124 may be a GPS receiver that receives location information from one or more positioning satellites. Alternately or in addition, the positioning element 124 may determine the user's location by measuring reception from one or more cellular towers, or may identify the user's location by identifying nearby wireless networks. For situations in which the systems discussed here collect information about users, the users may be provided with an opportunity to opt in/out of programs or features that may collect personal information (e.g., information about a user's location, a user's preferences or a user's contributions to social content providers). In addition, in some examples, certain data may be anonymized in one or more ways before it is stored or used, so that personally identifiable information is removed. For example, a user's identity and location may be anonymized so that the personally identifiable information cannot be determined or associated for the user and so that identified user preferences or user interactions are generalized (for example, generalized based on user demographics) rather than associated with a particular user. Aspects that rely on a user location may identify the location in a general manner. For example, the system may provide information in a binary manner (e.g., a user is nearby, or they are not nearby) rather than specifically identifying a proximity or location.

The navigation application 130 may use a map model 132 stored in the data 128 to perform navigation operations. As described with respect to the server 102, the client 104 may store a copy of the map model 118 that may include a series of polygons and adjacency relationships between those polygons, where the polygons correspond to navigable areas of a floor plan. An example of a method for performing routing functions using such a map model is described below (see FIG. 5).

The network 134, and the intervening nodes between the server 102 and the client 104 may comprise various configurations and use various protocols including the Internet, World Wide Web, intranets, virtual private networks, local Ethernet networks, private networks using communication protocols proprietary to one or more companies, cellular and wireless networks (e.g., Wi-Fi), instant messaging, hypertext transfer protocol (“HTTP”) and simple mail transfer protocol (“SMTP”), and various combinations of the foregoing. It should be appreciated that a typical system may include a large number of connected computers.

Although certain advantages are obtained when information is transmitted or received as noted above, other aspects of the system and method are not limited to any particular manner of transmission of information. For example, in some aspects, information may be sent via a medium such as an optical disk or portable drive. In other aspects, the information may be transmitted in a non-electronic format and manually entered into the system.

FIG. 2 is block diagram depicting an example of a map model 202 generated from a floor plan 200 in accordance with aspects of the disclosure. One example of a method for generating a map model for use in navigation operations involves analysis of an image associated with a building floor plan. Analysis of this image allows for identification of navigable areas and non-navigable areas. The navigable areas may be filled with convex polygons, and adjacency relationships between the polygons may be used to assist with navigation operations.

As described above with respect to FIG. 1, the floor plan may be provided in any format readable by a computer, including various file formats, such as GIF, JPEG, PDF, TIFF, BMP, DXF, etc. Areas of navigable space within the floor plan may be associated with one or more colors present within the image, and areas of non-navigable space may be associated with another set of one or more colors. The color assignments may be performed manually by a user, or automatically using an image analysis algorithm. The term “color” is broadly understood to refer to elements that define an image pixel. The features analyzed by aspects of the disclosure may also include brightness, luminosity, grayscale, or any other feature that may distinguish whether a particular pixel is associated with navigable space or non-navigable space.

An analysis operation may begin by identifying a first pixel in an upper left corner of the image, such as the pixel 206. The color of this pixel 206 may be analyzed to determine whether the pixel corresponds to navigable space or non-navigable space. If the currently analyzed pixel corresponds to navigable space, the analysis operation may expand outward from the pixel in 8 directions, such as shown in element 204 of FIG. 2. In this instance, the pixel 206 has navigable areas to the right, lower-right, and below, so the analysis would next proceed to those pixels. The pixel 208 represents the start of a new polygon that might be reached from continued analysis of pixels adjacent to the initial pixel 206. The pixel 208 has open space to above, above-right, right, below-right, and below, to start forming a new polygon. In this manner, each pixel of the floor plan may be analyzed to identify areas of navigable space.

Areas of non-navigable space (e.g., walls) may be identified by their association with the second set of one or more colors. These non-navigable areas may be extrapolated to identify one or more convex polygons that fill the navigable space. For example, the floor plan 200 may be divided into a set of polygons A-K as depicted in the example map model 202. The polygons that fill the navigable space may further be analyzed to identify adjacency relationships, depicted as the shaded lines between adjacent polygons. The map model 202 may be converted into a data structure where each polygon is identified by a series of vertices (e.g., corners of the polygon) and a list of adjacent polygons. These vertices may correspond to map coordinates, latitudes and longitudes, or any other method of identifying the relationship between the area encompassed by the polygon in the map model and the navigable space in the mapped area defined by the floor plan.

In some aspects, the image analysis may also identify one or more image tags, such as the room tag 210. These tags may be associated with text strings and identified by optical character recognition (OCR) techniques. These image tags may be used to associate polygons with particular elements of the image. For example, a room may be labeled as “Conference Room A.” When that room is analyzed to generate the map model, this text may be recognized and stored in the map model as metadata associated with the polygon corresponding to the room for the purpose of route-finding operations. The user may then be routed to that room when requesting navigation instructions to “Conference Room A.”

FIG. 3 is a diagram depicting an example of a map model overlaid on a floor plan image in accordance with aspects of the disclosure. As shown in the image, navigable areas of an office building floor plan (e.g., hallways, doorways, rooms, and the like) have been divided into a series of polygons A-OO. In the instant example, these polygons are associated with pixels having a gray color. Convex polygons, such as the polygons depicted in the image, may be used to ensure that any given pair of polygons has at most one common side/adjacency relationship. If a user is within polygon A and wishes to travel to an area associated with polygon B, a navigation application may analyze adjacency relationships present within the image map to route the user via polygons F, G, and H to arrive at polygon B. An example of a method for performing routing operations using such a map model is described further below (see FIG. 5).

FIG. 4 is a flow diagram depicting an example of a method 400 for generating a map model from a floor plan image in accordance with aspects of the disclosure. The method 400 is operable to analyze an image corresponding to a floor plan, and generate a map model suitable for performing navigation operations from the analysis. A computer, such as the server 102 described with respect to FIG. 1, may analyze pixels of the floor plan image to determine whether each pixel corresponds to navigable space or non-navigable space. Areas of navigable space may be filled with convex polygons, and adjacency relationships between these convex polygons may be used to perform routing and navigation operations.

At stage 402, colors are identified for navigable areas and non-navigable areas. Navigable areas are generally areas in which travel and navigation is possible, such as hallways, doorways, open space, sidewalks, roads, and the like. Non-navigable areas are areas through which travel is obstructed, such as walls, shrubbery, landscaping, and the like. Certain colors may be assigned to navigable areas, and other colors assigned to non-navigable areas. Certain colors may be designated as navigable and all others designated as non-navigable, or any other method of assigning colors to differentiate between navigable areas and non-navigable areas. For example, navigable areas may be associated with the color gray, and non-navigable areas with the color black, navigable areas may be associated with the color white, and non-navigable areas associated with any non-white color, or navigable areas maybe associated with the colors blue and green, and non-navigable areas associated with the colors red and black. In some aspects, colors may be automatically assigned to navigable and non-navigable areas based on analysis of the image.

At stage 404, an initial pixel of navigable space is identified for analysis. At the start of the analysis, a pixel in the upper left corner of the image may be identified as the initial pixel. Each pixel in sequence may be analyzed starting in the upper left corner until a pixel of navigable space is identified. A pixel may be identified as navigable space if the pixel is associated with a color identified as associated with a navigable area at stage 402. If the analysis is already underway, then an initial pixel may be identified in relation to a previously defined polygon within the image. For example, the pixel of navigable space closest to the upper left corner of the image that is not already within a defined polygon may begin another round of analysis. As the analysis expands from pixels of navigable space, areas of non-navigable space are identified by their association with the colors of non-navigable space determined at stage 402. These areas of non-navigable space may be used to determine the borders of one or more polygons that identify navigable space.

Each pixel of the floor plan image may be associated with a particular set of latitude and longitude coordinates, or any other set of data suitable for associating the floor plan to a corresponding navigable area. This association data may be included in image metadata, or it may be provided separately during the map model generation process, such as by selecting a particular building that the floor plan describes. A relative set of coordinates may also be used. For example, a point on the map may be designated as the origin, and every other point on the map may be identified relative to the origin. Indoor navigation techniques that correspond to this relative coordinate system may be employed (e.g., calibration based on indoor landmarks associated with relative coordinates).

At stage 406, a polygon may be created by expanding from the initial pixel. For example, the polygon may be defined by analyzing pixels in 8 directions from the initial pixel to determine areas of navigable space around the initial pixel, such as described above with respect to FIG. 2. The method may explicitly define convex polygons within the image to ensure that each set of two polygons has no more than a single line segment in common. Polygon boundaries may be determined by identifying locations of non-navigable space, and extrapolating the boundaries of the polygon from the non-navigable space to ensure the polygons remain convex. In one example, polygon boundaries are identified by expanding from an initial pixel in a clockwise manner. When exploring the map, polygon boundaries may be identified by moving clockwise from the current pixel. By constraining analysis in this manner and tracking the area of the polygon that has already been defined, the open space will always be divided into convex polygons. A polygon is thus defined that encompasses as much navigable space as possible while remaining convex and not overlapping with any non-navigable space.

At stage 408, a determination is made as to whether all navigable space within the floor plan image is associated with a polygon. For example, the pixel analysis of stages 404 and 406 may identify areas of navigable space that cannot be associated with a convex polygon. These areas of navigable space may thus be separately analyzed for creation of a new polygon to ensure that all navigable space is associated with a polygon that may later be used for route finding operations. Alternately, each pixel of the floor plan that has not been associated with a polygon may be analyzed to ensure that each area of navigable space is associated with a polygon, even if that polygon is not adjacent with any previously mapped polygons. If unassociated navigable space remains, the method returns to stage 404 to continue the analysis. If all navigable space has been identified and associated with a polygon, the method proceeds to stage 410.

At stage 410, the polygons associated with the areas of navigable space are associated with any identifiers present within the floor plan. For example, the floor plan may label hallways, corridors, or rooms with text labels to designate the name of the particular hall, corridor, or room. In this manner, a polygon that is associated with a particular room may be given a name for that room, such as “Conference Room A.” If the floor plan does not include labels, the polygons may be assigned particular labels by the processing system. Each polygon may be associated with a unique label, or other data describing the area encompassed by the polygon. The method may also identify other features and data describing the polygon and its relationship to the original floor plan, which may also be associated and stored with the polygon in a map model of the area associated with the floor plan.

At stage 412, a map model is generated using the polygons created at stage 406. The map model includes vertices that define each polygon and adjacency relationships between the polygons. Each vertex may be associated with a set of latitude and longitude coordinates, or any other method of associating a particular polygon to a particular area of space for the purpose of navigation and route finding operations. The data structure associated with the map model may include a series of vertices defining each polygon and a list of adjacency relationships between the polygons. The method 400 ends after generation of the map model.

FIG. 5 is a flow diagram depicting an example of a method 500 for navigating using an indoor map model in accordance with aspects of the disclosure. A map model as described above (see FIGS. 1-4) may be used to perform navigation operations on a client. The map model may comprise a series of convex polygons defined by vertices, and adjacency relationships between those polygons. A client may determine an initial location using a navigation element, and use the initial location to identify a source polygon. The client may determine a route to a destination by creating a path through a series of polygons that are adjacent to one another, where the final polygon in the path is associated with the destination. Performing route finding operations in this manner ensures that a path exists for all source locations to all destination locations, providing the entire navigable area is associated with polygons in some form of adjacency relationship.

At stage 502, the current location of the client is determined. The current location may be determined by a navigation element of the client device (see FIG. 1). As described above, the navigation element may determine the current location of the client in a variety of manners, including but not limited to using GPS satellites, identification of cellular towers, identification of wireless networks, or any other method suitable for identifying an initial position of the client. For example, the navigation element may comprise a GPS receiver that provides a set of latitude and longitude coordinates for the client device.

At stage 504, a source polygon is identified using the current location obtained at stage 502. By defining each polygon as the area bounded by line segments connecting a series of vertices, where the vertices are each associated with a coordinate, it is relatively simple computationally to determine whether the current location falls within a particular polygon. For example, if a polygon is defined by four vertices at ordinal coordinates (0,0), (2,0), (2,2), and (0, 2), the point (1,1) would be contained within the space defined by the four vertices. Implementations of the method may rely on the use of convex polygons, ensuring that each set of vertices completely encloses a given set of navigable space, further simplifying the process of determining whether a given point is within the polygon.

At stage 506, a polygon associated with a destination is determined. The user may enter a destination on the client by inputting a text string or selecting a destination from a menu. The user may also be presented with the map model overlaid on a floor plan, such as to enable touch screen selection of the destination. As with the user's current location, the destination is associated with a particular polygon. The destination may be located within a polygon, or adjacent to a polygon, depending upon whether the destination is defined as a navigable area (and thus within a polygon), or a non-navigable area (and thus not within a polygon). The destination may be identified using a particular map tag extracted from the floor plan image during generation of the map model (see FIG. 2).

After determining a polygon associated with the destination, at stage 508 a route from the source polygon to the destination polygon is identified using adjacency relationships between the polygons. Various methods may be used to identify a path across adjacency relationships between the source polygon and the destination polygon, including common searching algorithms such as, for example Djikstra's shortest path algorithm or a Breadth First Search. The path to the destination across the adjacent polygons may be provided to the user to assist with navigation operations, such as by providing directions to the next polygon in the route using adjacency information, or by highlighting the series of polygons on a map overlay.

The stages of the illustrated methods are not intended to be limiting. The functionality of the methods can exist in a fewer or greater number of stages than what is shown and, even with the depicted methods, the particular order of events may be different from what is shown in the figures.

The systems and methods described herein advantageously provide an efficient map model for use in navigation operations. The map model may include a simplified representation of a navigable area compared to traditional road graph implementations, such that navigable areas are represented by a series of vertices defining convex polygons, and a set of adjacency relationships among the polygons. The map model may be particularly well suited for indoor navigation operations, which are typically performed by mobile devices that may lack processing power compared to vehicle mounted navigation systems. Furthermore, the map model described may be particularly useful for indoor navigation operations since the polygon representation described ensures that, as long as the navigable area is contiguous, any two points within the navigable area have a path between the two points, unlike road graph implementations which sometimes include approximations based on nearest paths. Such an implementation solves the so-called “pedestrian problem” where a nearest road line segment is not necessarily the optimal path to travel to a given point that exists external to the road graph, thus failing to provide an optimal path to a pedestrian traveler, who is not bound by to particular roads.

As these and other variations and combinations of the features discussed above can be utilized without departing from the disclosure as defined by the claims, the foregoing description of the embodiments should be taken by way of illustration rather than by way of limitation of the disclosure as defined by the claims. It will also be understood that the provision of examples of the disclosure (as well as clauses phrased as “such as,” “e.g.”, “including” and the like) should not be interpreted as limiting the disclosure to the specific examples; rather, the examples are intended to illustrate only some of many possible embodiments. 

1. A computer implemented method for providing indoor navigation, the method comprising: determining a client location; identifying the client location as being within a source polygon selected from a plurality of convex polygons, the plurality of convex polygons defined by a map model that comprises the plurality of convex polygons and a set of adjacency relationships among the plurality of convex polygons, the plurality of convex polygons being associated with navigable space within a given geographical area; receiving a destination location; determining whether the destination location is located within navigable space or a non-navigable area; determining a destination polygon based on the determination of whether the destination location is located within navigable space or the non-navigable area; determining, with one or more processors, a route from the source polygon to the destination polygon using the map model by identifying a path defined by the set of adjacency relationships; and providing the route from the source polygon to the destination polygon as a navigation path from the client location to the destination location; wherein the borders of each convex polygon is determined at least in part by the one or more processors identifying an initial navigable pixel and expanding the border in a direction away from the initial navigable pixel until reaching at least one pixel associated with non-navigable space in said direction, and the one or more processors provides the borders to the client device.
 2. The method of claim 1, wherein the set of adjacency relationships are line segments representing the boundaries between polygons.
 3. The method of claim 1, wherein the plurality of convex polygons define the entirety of navigable space in an area.
 4. The method of claim 3, wherein the navigable space is contiguous.
 5. The method of claim 1, wherein the map model is generated using a building floor plan.
 6. The method of claim 1, wherein the map model further comprises metadata associated with one or more of the plurality of polygons and wherein the method further comprises determining the destination polygon by searching the metadata.
 7. The method of claim 1, wherein the map model comprises a series of vertices that define the plurality of polygons, wherein the series of vertices are associated with location coordinates within the given geographical area.
 8. A method comprising: determining a first location; identifying, using one or more processors, the first location as being within a source polygon selected from a plurality of polygons, the plurality of polygons defined by a map model that comprises the plurality of polygons and a set of adjacency relationships among the plurality of polygons, the plurality of polygons being associated with navigable space within a given geographical area; receiving a destination location; determining a destination polygon based on whether the destination location is located within navigable space or non-navigable space; determining, using the one or more processors, a route from the source polygon to the destination polygon using the map model by identifying a path defined by the set of adjacency relationships; and providing the route from the source polygon to the destination polygon as a navigation path from the first location to the destination location; wherein the borders of each polygon is determined at least in part by identifying an initial navigable pixel and expanding the border in a direction away from the initial navigable pixel until reaching at least one pixel associated with non-navigable space in said direction.
 9. The method of claim 8, wherein the set of adjacency relationships are line segments representing the boundaries between polygons.
 10. The method of claim 8, wherein the plurality of polygons define the entirety of navigable space in an area.
 11. The method of claim 10, wherein the navigable space is contiguous.
 12. The method of claim 8, wherein the map model is generated using a building floor plan.
 13. The method of claim 8, wherein the map model further comprises metadata associated with one or more of the plurality of polygons and wherein the method further comprises determining the destination polygon by searching the metadata.
 14. The method of claim 8, wherein the map model comprises a series of vertices that define the plurality of polygons, wherein the series of vertices are associated with location coordinates within the given geographical area, and wherein the polygons are convex.
 15. A system for providing indoor navigation comprising: a navigation element for providing the current location of a device; one or more processors; and a memory accessible by the one or more processors, the memory comprising a map model that includes a plurality of convex polygons and a set of adjacency relationships among the plurality of convex polygons, the plurality of convex polygons being associated with navigable space within a given geographical area, wherein the navigable space is determined by identifying a navigable pixel and analyzing adjacent pixels to identify one or more boundaries of the plurality of convex polygons by extrapolating one or more non-navigable areas; the memory further comprising instructions executable by the one or more processors, the instructions comprising: identifying the current location provided by the navigation element as being within a source polygon selected from the plurality of convex polygons; receiving a destination location; determining whether the destination location is located within navigable space or a non-navigable space; determining a destination polygon based on the determination of whether the destination location is located within navigable space or the non-navigable space; determining a route from the source polygon to the destination polygon using the map model by identifying a path defined by the set of adjacency relationships; providing the route from the source polygon to the destination polygon as a navigation path from the client location to the destination location; wherein the borders of each convex polygon is determined at least in part by one or more processors identifying an initial navigable pixel and expanding the border in a direction away from the initial navigable pixel until reaching at least one pixel associated with non-navigable space in said direction.
 16. The system of claim 15, wherein the set of adjacency relationships are line segments representing the boundaries between polygons.
 17. The system of claim 15, wherein the plurality of convex polygons define the entirety of navigable space in an area.
 18. The system of claim 17, wherein the navigable space is contiguous.
 19. The system of claim 15, wherein the map model is generated using a building floor plan.
 20. The system of claim 15, wherein the map model further comprises metadata associated with one or more of the plurality of polygons and the instructions further comprise determining the destination polygon by searching the metadata. 